Scaled UI Jettons #526

krigga · 2025-09-19T12:47:46Z

No description provided.

ProgramCrafter · 2025-09-22T11:42:46Z

text/0000-scaled-ui-jettons.md

+
+   `onchain_balance` - (integer) - the balance of a jetton wallet or a transfer amount as reported by `get_wallet_data()` call on the jetton wallet or in onchain data
+
+   `displayed_balance` - (integer) - the equivalent amount that should be displayed in UIs


That sounds imprecise; after all, not even nanoTON amount is displayed in UIs as is. Maybe do a [int userfacing_numerator, int userfacing_denominator], or a fixed-point fraction (with denominator of either 2^64, 2^128 or 10^18)?

muldiv internally uses 513 bits for calculation instead of 257. And standard is not limited to this. Arbitrary implementation may include numerator/denominator. The key point here is that we delegate this logic to the contract implementation.

text/0000-scaled-ui-jettons.md

@ProgramCrafter I have added a remark to hopefully resolve the confusion around the usage of decimals.

mr-tron · 2025-09-23T12:06:49Z

I see two problems in this TEP.

How it should be displayed in user history? For example somebody had 100 real token and multiplier was x2 so wallet displayed him 200. Ok. He send 100 to his friend (real 50). I think wallet should displayed 100 outgoing tokens in history. But few days later multiplicator was updated and now it x4. What wallet should displayed in history? Still 100? But it creates big problem for indexer because it need to calculate master state at the moment of transfer transaction. And I even don't touch problem what jetton transfer in ton has two transactions and master state can be changed between them.
Potential DDoS to wallet infrastructure. Now indexer calculates jetton balances one time (on last transaction) and on then you requests list of jetton balances it's one select to database select jetton, balance from jetton_wallet where owner = $account . But with new standard on every balance request server should make tvm call on every jetton with this feature. So i just need to deploy 1000 Scaled UI jettons and send them to someone and his request for balances 1) becomes very slow 2) need a lot of computations.

ProgramCrafter · 2025-09-23T12:51:16Z

This is elegantly solved by requiring custom payload to contain the active multiplier. This solution also has the side benefit of supporting true rebase jettons, but its drawback is that it starts prying into custom payload contents.

0979478318za-M2ooTaz1 · 2025-09-24T13:16:43Z

text/0526-scaled-ui-jettons.md

text/0000-scaled-ui-jettons.md

0979478318za-M2ooTaz1 · 2025-09-24T13:17:23Z

text/0000-scaled-ui-jettons.md

+
+   `onchain_balance` - (integer) - the balance of a jetton wallet or a transfer amount as reported by `get_wallet_data()` call on the jetton wallet or in onchain data
+
+   `displayed_balance` - (integer) - the equivalent amount that should be displayed in UIs


text/0000-scaled-ui-jettons.md

shuva10v · 2025-09-24T13:54:15Z

text/0000-scaled-ui-jettons.md

+They MUST additionally (w.r.t. TEP-74) support the following get methods:
+1. `get_supply_data()` returns `(int total_onchain_supply, int total_displayed_supply)`
+
+   `total_onchain_supply` - (integer) - the sum of balances of jetton wallets of this jetton master (as reported by `get_wallet_data()` calls on the jetton wallets)


it should be equal to the total_supply field from the get_jetton_data, shouldn't it? If so I propose to return only the total_displayed_supply here and reuse existing get method. Otherwise developers could create implementation which returns different values

It should, and I will rewrite the text to say so. However I think returning both values at the same time is necessary so as to avoid a situation where one get method returns a value from state A and the next call to another get method returns a value from state B, resulting in inconsistent calculations.

Kaladin13 · 2025-09-24T14:15:43Z

Potential DDoS to wallet infrastructure. Now indexer calculates jetton balances one time (on last transaction) and on then you requests list of jetton balances it's one select to database select jetton, balance from jetton_wallet where owner = $account . But with new standard on every balance request server should make tvm call on every jetton with this feature. So i just need to deploy 1000 Scaled UI jettons and send them to someone and his request for balances 1) becomes very slow 2) need a lot of computations.

I guess indexers could apply the same approach to this as with regular jetton balances - index latest multiplier change on master contract (if we accept this TEP then we can detect it) and store it for corresponding jetton. With this, retrieving balance for user will still be one select, without the need to run tvm call every time.

…tandard. Add an external-out message to report supply data changes.

krigga · 2025-09-25T12:14:08Z

@mr-tron @Kaladin13 I have changed the TEP to hopefully allow for a simpler indexer implementation

chakzefir · 2025-10-07T15:14:19Z

What about existing Jetton contracts? Should we consider implementing a workaround to give them the same level of visibility in the interfaces?

krigga · 2025-10-13T15:04:35Z

What about existing Jetton contracts? Should we consider implementing a workaround to give them the same level of visibility in the interfaces?

In a similar way to TEP-89?

(quote from TEP-89)

For non-upgradable Jetton Master with updatable metadata it is recommended to add "wallet-discovery" key with value equal to text representaion of Jetton Discovery contract address.

…layed supply

1IxI1 · 2025-10-20T15:20:47Z

text/0000-scaled-ui-jettons.md

+
+Jetton master contracts supporting this TEP MUST send the following external-out message (TL-B structure) whenever the values returned by `get_display_multiplier()`:
+```
+display_multiplier_changed#ac392598 numerator:(VarUInteger 32) denominator:(VarUInteger 32) {n:#} comment:(Maybe (SnakeData ~n)) = ExternalOutMsgBody;


wrong scheme. should be

display_multiplier_changed#ac392598 numerator:(VarUInteger 32) denominator:(VarUInteger 32) {n:#} comment:(Maybe (SnakeData n)) = ExternalOutMsgBody n;

or better

display_multiplier_changed#ac392598 numerator:(VarUInteger 32) denominator:(VarUInteger 32) comment:(Maybe SnakeString) = ExternalOutMsgBody;

(SnakeString probably gonna be added to tlbc soon, yet it's on this branch. your SnakeData type is not defined anyway)

chore: update external-out schema chore: replace TBDs

krigga · 2025-10-23T14:12:05Z

What about existing Jetton contracts? Should we consider implementing a workaround to give them the same level of visibility in the interfaces?

I have added this into the standard, however I am now being told by multiple members of the community that this is not a good addition.

I invite the community to discuss this and/or vote on whether this feature should be removed (specifically, these lines https://github.com/ton-blockchain/TEPs/pull/526/files#diff-837a6387eab3bd4d428b9d6a741cf8f2e14dd62adee63ab40c0eada0c73c37a4R56-R58).

Please leave a 👍 reaction to vote for REMOVAL of the feature, and 👎 to vote to LEAVE/INCLUDE the feature in the standard.

mr-tron

LGTM

Scaled UI Jettons

27926ec

ProgramCrafter reviewed Sep 22, 2025

View reviewed changes

chore: describe edge cases

23148b8

0979478318za-M2ooTaz1 reviewed Sep 24, 2025

View reviewed changes

shuva10v reviewed Sep 24, 2025

View reviewed changes

krigga added 2 commits September 25, 2025 15:08

Remove the calculation get methods, describe the calculation in the s…

7433a40

…tandard. Add an external-out message to report supply data changes.

Add a clarification about decimals.

dff99b6

Add comment to external-out message

b9beca3

krigga and others added 2 commits October 14, 2025 18:20

feat: make the multiplier an abstract number, instead of a total disp…

ca172ea

…layed supply

chore: clarifty get method return values

8ebee92

1IxI1 reviewed Oct 20, 2025

View reviewed changes

krigga added 2 commits October 20, 2025 21:18

chore: add reference implementation link

1813a72

chore: update external-out schema chore: replace TBDs

chore: add init event requirement

75e618a

krigga and others added 2 commits October 26, 2025 18:59

chore: remove section for already existing contracts

a3e7e1d

chore: rename file and mention in README

a635c6c

ton-blockchain deleted a comment from Rastakhcarbon Nov 13, 2025

mr-tron reviewed Nov 13, 2025

View reviewed changes

EmelyanenkoK merged commit 174817a into ton-blockchain:master Nov 13, 2025


		`onchain_balance` - (integer) - the balance of a jetton wallet or a transfer amount as reported by `get_wallet_data()` call on the jetton wallet or in onchain data

		`displayed_balance` - (integer) - the equivalent amount that should be displayed in UIs

Scaled UI Jettons #526

Scaled UI Jettons #526

Conversation

krigga commented Sep 19, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mr-tron commented Sep 23, 2025

Uh oh!

ProgramCrafter commented Sep 23, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Kaladin13 commented Sep 24, 2025

Uh oh!

krigga commented Sep 25, 2025

Uh oh!

chakzefir commented Oct 7, 2025

Uh oh!

krigga commented Oct 13, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

krigga commented Oct 23, 2025

Uh oh!

mr-tron left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

10 participants